Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Josh Kutsko #7

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Josh Kutsko #7

wants to merge 2 commits into from

Conversation

jkutsko
Copy link

@jkutsko jkutsko commented Feb 18, 2016

No description provided.


### Interface (syntax)
_How might the user interact with the language? What does programming look
like? Why is this the right way to interact with the problem domain?_

The user would interact with this language just by writing scripts in either the shell, or a text editor. I'm imagining commands like:
Hero {item1, item2, item3, item4, item5, item6} level 15;
printing out the relevant stats for that hero. The core issue seems to be text or GUI as the core interaction. I claim that text is probably faster, as you could much mroe easily copy and paste the same 6 items into different heroes, rather than having to reselect everything every time. Text makes things like standard batch testing much easier than a GUI on its own.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be cool if you could specify at which level each item was acquired. Then in the output you could have the hero's stats over some sort of time (or level) axis. Then you'd be able to guage that specific build's strenghts + weaknesses in the early, mid, and late game. Though maybe this would expand the scope of the project too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants